Method and apparatus for supporting machine-type communications with a mobile-originated-only mode

ABSTRACT

A method and apparatus for supporting machine-type communications (MTC) are disclosed. A wireless transmit/receive unit (WTRU) may configure itself to operate in a mobile-originated-only mode. The WTRU may perform no, or a subset of, radio resource control (RRC) idle and/or non-access stratum (NAS) idle/standby state procedures in the mobile-originated-only mode. For example, the WTRU may perform cell reselection but not paging monitoring in the mobile-originated-only mode. Alternatively, the WTRU may perform paging monitoring but not cell reselection and location update. The operation in the mobile-originated-only mode may be triggered explicitly or implicitly. For example, the WTRU may operate in the mobile-originated-only mode if an inactivity timer expires. The WTRU may switch the mode in accordance with a pre-configured schedule. After transition of the operation mode, the WTRU may send a message to the network indicating such mode switch.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.14/559,470, filed Dec. 3, 2014; which is a continuation of U.S. patentapplication Ser. No. 14/270,063, filed May 5, 2014, now U.S. Pat. No.9,008,643; which is a continuation of U.S. patent application Ser. No.13/025,675 filed Feb. 11, 2011, now U.S. Pat. No. 8,755,825, whichclaims the benefit of U.S. Provisional Application Ser. No. 61/304,383filed Feb. 12, 2010, and this application claims the benefit of thefiling date of all of these applications and hereby incorporates theircontents by reference.

BACKGROUND

Machine-type communication (MTC) is a communication involving one ormore entities that do not necessarily need human interaction. The MTCmay involve a large number of communicating MTC devices, (i.e., wirelesstransmit/receive units (WTRUs) that are equipped for MTC), with no orlittle traffic destined to the MTC devices, (e.g., sensor networks). TheMTC devices may be battery operated, and therefore saving batteryconsumption and allowing for longer operation without manualintervention would be necessary.

In MTC, in some use cases, a device may be required to support mobileoriginated communications only, (e.g., a metering system whichperiodically reports measurements). Where it is expected that a devicemay initiate or receive calls, the network should know the location ofthe device, (i.e., which cell or area the device is located), even whenthe device is in an idle mode, so that when a call needs to be made tothat device, the call can be completed timely. However, if the deviceonly makes calls, but never receives calls, the location of the devicebecomes less important, since the network does not need to find thedevice. In other use cases, a device may be required to supportinfrequent mobile terminated communications, (e.g., a metering systemthat supports device polling by the network).

SUMMARY

A method and an apparatus for supporting machine-type communications aredisclosed. A WTRU may configure itself to operate in amobile-originated-only mode based on a trigger. The WTRU may perform no,or a subset of, radio resource control (RRC) idle and/or non-accessstratum (NAS) idle/standby state procedures in themobile-originated-only mode. For example, the WTRU may perform cellreselection but not paging monitoring in the mobile-originated-onlymode. Alternatively, the WTRU may perform paging monitoring but not cellreselection and location update. The operation in themobile-originated-only mode may be triggered explicitly or implicitly.For example, the WTRU may initiate operation in themobile-originated-only mode if an inactivity timer expires. The WTRU mayswitch the mode in accordance with a pre-configured schedule. Aftertransition of the operation mode, the WTRU may or may not send a messageto the network indicating such mode switch.

The operations in the mobile-originated-only mode may be supported byadding some modifications to RRC and/or NAS procedures. In order toaccomplish the modifications, implementation may be made by using aseparate RRC idle state, an RRC idle mode with a profile configurationconfigured for the mobile-originated-only mode, or a mobile originateonly state in an RRC idle mode. Similarly, the NAS modifications may bemade by either supporting a new NAS state or by using a new profileconfiguration in the mobile-originated-only mode.

Embodiments to support a new mode of operation referred to as“mobile-originated-only mode” are disclosed. This new mode of operationmay be implemented using a new “mobile-originated-only state” or a newprofile configuration for the RRC and/or NAS layers. The WTRU may send amessage to a network indicating that the WTRU supports themobile-originated-only mode and/or functionalities supported by the WTRUin the mobile-originated-only mode.

BRIEF DESCRIPTION OF THE DRAWINGS

A more detailed understanding may be had from the following description,given by way of example in conjunction with the accompanying drawingswherein:

FIG. 1A is a system diagram of an example communications system in whichone or more disclosed embodiments may be implemented;

FIG. 1B is a system diagram of an example wireless transmit/receive unit(WTRU) that may be used within the communications system illustrated inFIG. 1A;

FIG. 1C is a system diagram of an example radio access network and anexample core network that may be used within the communications systemillustrated in FIG. 1A;

FIG. 1D is an example communication case where MTC devices communicatewith an MTC server;

FIG. 2 shows a transition between the mobile-originated-only mode andthe mobile-originated-and-terminated mode;

FIG. 3 is an example universal terrestrial radio access (UTRA) RRC statediagram in accordance with one embodiment;

FIG. 4 is an example evolved universal terrestrial radio access (E-UTRA)RRC state diagram in accordance with one embodiment; and

FIG. 5 is an example reachable period and unreachable period.

DETAILED DESCRIPTION

FIG. 1A is a diagram of an example communications system 100 in whichone or more disclosed embodiments may be implemented. The communicationssystem 100 may be a multiple access system that provides content, suchas voice, data, video, messaging, broadcast, etc., to multiple wirelessusers. The communications system 100 may enable multiple wireless usersto access such content through the sharing of system resources,including wireless bandwidth. For example, the communications systems100 may employ one or more channel access methods, such as code divisionmultiple access (CDMA), time division multiple access (TDMA), frequencydivision multiple access (FDMA), orthogonal FDMA (OFDMA), single-carrierFDMA (SC-FDMA), and the like.

As shown in FIG. 1A, the communications system 100 may include wirelesstransmit/receive units (WTRUs) 102 a, 102 b, 102 c, 102 d, a radioaccess network (RAN) 104, a core network 106, a public switchedtelephone network (PSTN) 108, the Internet 110, and other networks 112,though it will be appreciated that the disclosed embodiments contemplateany number of WTRUs, base stations, networks, and/or network elements.Each of the WTRUs 102 a, 102 b, 102 c, 102 d may be any type of deviceconfigured to operate and/or communicate in a wireless environment. Byway of example, the WTRUs 102 a, 102 b, 102 c, 102 d may be configuredto transmit and/or receive wireless signals and may include userequipment (UE), a mobile station, a fixed or mobile subscriber unit, apager, a cellular telephone, a personal digital assistant (PDA), asmartphone, a laptop, a netbook, a personal computer, a wireless sensor,consumer electronics, and the like.

The communications systems 100 may also include a base station 114 a anda base station 114 b. Each of the base stations 114 a, 114 b may be anytype of device configured to wirelessly interface with at least one ofthe WTRUs 102 a, 102 b, 102 c, 102 d to facilitate access to one or morecommunication networks, such as the core network 106, the Internet 110,and/or the networks 112. By way of example, the base stations 114 a, 114b may be a base transceiver station (BTS), a Node-B, an eNode B, a HomeNode B, a Home eNode B, a site controller, an access point (AP), awireless router, and the like. While the base stations 114 a, 114 b areeach depicted as a single element, it will be appreciated that the basestations 114 a, 114 b may include any number of interconnected basestations and/or network elements.

The base station 114 a may be part of the RAN 104, which may alsoinclude other base stations and/or network elements (not shown), such asa base station controller (BSC), a radio network controller (RNC), relaynodes, etc. The base station 114 a and/or the base station 114 b may beconfigured to transmit and/or receive wireless signals within aparticular geographic region, which may be referred to as a cell (notshown). The cell may further be divided into cell sectors. For example,the cell associated with the base station 114 a may be divided intothree sectors. Thus, in one embodiment, the base station 114 a mayinclude three transceivers, i.e., one for each sector of the cell. Inanother embodiment, the base station 114 a may employ multiple-inputmultiple output (MIMO) technology and, therefore, may utilize multipletransceivers for each sector of the cell.

The base stations 114 a, 114 b may communicate with one or more of theWTRUs 102 a, 102 b, 102 c, 102 d over an air interface 116, which may beany suitable wireless communication link (e.g., radio frequency (RF),microwave, infrared (IR), ultraviolet (UV), visible light, etc.). Theair interface 116 may be established using any suitable radio accesstechnology (RAT).

More specifically, as noted above, the communications system 100 may bea multiple access system and may employ one or more channel accessschemes, such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA, and the like. Forexample, the base station 114 a in the RAN 104 and the WTRUs 102 a, 102b, 102 c may implement a radio technology such as Universal MobileTelecommunications System (UMTS) Terrestrial Radio Access (UTRA), whichmay establish the air interface 116 using wideband CDMA (WCDMA). WCDMAmay include communication protocols such as High-Speed Packet Access(HSPA) and/or Evolved HSPA (HSPA+). HSPA may include High-Speed DownlinkPacket Access (HSDPA) and/or High-Speed Uplink Packet Access (HSUPA).

In another embodiment, the base station 114 a and the WTRUs 102 a, 102b, 102 c may implement a radio technology such as Evolved UMTSTerrestrial Radio Access (E-UTRA), which may establish the air interface116 using Long Term Evolution (LTE) and/or LTE-Advanced (LTE-A).

In other embodiments, the base station 114 a and the WTRUs 102 a, 102 b,102 c may implement radio technologies such as IEEE 802.16 (i.e.,Worldwide Interoperability for Microwave Access (WiMAX)), CDMA2000,CDMA2000 1×, CDMA2000 EV-DO, Interim Standard 2000 (IS-2000), InterimStandard 95 (IS-95), Interim Standard 856 (IS-856), Global System forMobile communications (GSM), Enhanced Data rates for GSM Evolution(EDGE), GSM EDGE radio access network (GERAN), and the like.

The base station 114 b in FIG. 1A may be a wireless router, Home Node B,Home eNode B, or access point, for example, and may utilize any suitableRAT for facilitating wireless connectivity in a localized area, such asa place of business, a home, a vehicle, a campus, and the like. In oneembodiment, the base station 114 b and the WTRUs 102 c, 102 d mayimplement a radio technology such as IEEE 802.11 to establish a wirelesslocal area network (WLAN). In another embodiment, the base station 114 band the WTRUs 102 c, 102 d may implement a radio technology such as IEEE802.15 to establish a wireless personal area network (WPAN). In yetanother embodiment, the base station 114 b and the WTRUs 102 c, 102 dmay utilize a cellular-based RAT (e.g., WCDMA, CDMA2000, GSM, LTE,LTE-A, etc.) to establish a picocell or femtocell. As shown in FIG. 1A,the base station 114 b may have a direct connection to the Internet 110.Thus, the base station 114 b may not be required to access the Internet110 via the core network 106.

The RAN 104 may be in communication with the core network 106, which maybe any type of network configured to provide voice, data, applications,and/or voice over internet protocol (VoIP) services to one or more ofthe WTRUs 102 a, 102 b, 102 c, 102 d. For example, the core network 106may provide call control, billing services, mobile location-basedservices, pre-paid calling, Internet connectivity, video distribution,etc., and/or perform high-level security functions, such as userauthentication. Although not shown in FIG. 1A, it will be appreciatedthat the RAN 104 and/or the core network 106 may be in direct orindirect communication with other RANs that employ the same RAT as theRAN 104 or a different RAT. For example, in addition to being connectedto the RAN 104, which may be utilizing an E-UTRA radio technology, thecore network 106 may also be in communication with another RAN (notshown) employing a GSM radio technology.

The core network 106 may also serve as a gateway for the WTRUs 102 a,102 b, 102 c, 102 d to access the PSTN 108, the Internet 110, and/orother networks 112. The PSTN 108 may include circuit-switched telephonenetworks that provide plain old telephone service (POTS). The Internet110 may include a global system of interconnected computer networks anddevices that use common communication protocols, such as thetransmission control protocol (TCP), user datagram protocol (UDP) andthe internet protocol (IP) in the TCP/IP internet protocol suite. Thenetworks 112 may include wired or wireless communications networks ownedand/or operated by other service providers. For example, the networks112 may include another core network connected to one or more RANs,which may employ the same RAT as the RAN 104 or a different RAT.

Some or all of the WTRUs 102 a, 102 b, 102 c, 102 d in thecommunications system 100 may include multi-mode capabilities, i.e., theWTRUs 102 a, 102 b, 102 c, 102 d may include multiple transceivers forcommunicating with different wireless networks over different wirelesslinks. For example, the WTRU 102 c shown in FIG. 1A may be configured tocommunicate with the base station 114 a, which may employ acellular-based radio technology, and with the base station 114 b, whichmay employ an IEEE 802 radio technology.

FIG. 1B is a system diagram of an example WTRU 102. As shown in FIG. 1B,the WTRU 102 may include a processor 118, a transceiver 120, atransmit/receive element 122, a speaker/microphone 124, a keypad 126, adisplay/touchpad 128, non-removable memory 106, removable memory 132, apower source 134, a global positioning system (GPS) chipset 136, andother peripherals 138. It will be appreciated that the WTRU 102 mayinclude any sub-combination of the foregoing elements while remainingconsistent with an embodiment.

The processor 118 may be a general purpose processor, a special purposeprocessor, a conventional processor, a digital signal processor (DSP), aplurality of microprocessors, one or more microprocessors in associationwith a DSP core, a controller, a microcontroller, Application SpecificIntegrated Circuits (ASICs), Field Programmable Gate Array (FPGAs)circuits, any other type of integrated circuit (IC), a state machine,and the like. The processor 118 may perform signal coding, dataprocessing, power control, input/output processing, and/or any otherfunctionality that enables the WTRU 102 to operate in a wirelessenvironment. The processor 118 may be coupled to the transceiver 120,which may be coupled to the transmit/receive element 122. While FIG. 1Bdepicts the processor 118 and the transceiver 120 as separatecomponents, it will be appreciated that the processor 118 and thetransceiver 120 may be integrated together in an electronic package orchip.

The transmit/receive element 122 may be configured to transmit signalsto, or receive signals from, a base station (e.g., the base station 114a) over the air interface 116. For example, in one embodiment, thetransmit/receive element 122 may be an antenna configured to transmitand/or receive RF signals. In another embodiment, the transmit/receiveelement 122 may be an emitter/detector configured to transmit and/orreceive IR, UV, or visible light signals, for example. In yet anotherembodiment, the transmit/receive element 122 may be configured totransmit and receive both RF and light signals. It will be appreciatedthat the transmit/receive element 122 may be configured to transmitand/or receive any combination of wireless signals.

In addition, although the transmit/receive element 122 is depicted inFIG. 1B as a single element, the WTRU 102 may include any number oftransmit/receive elements 122. More specifically, the WTRU 102 mayemploy MIMO technology. Thus, in one embodiment, the WTRU 102 mayinclude two or more transmit/receive elements 122 (e.g., multipleantennas) for transmitting and receiving wireless signals over the airinterface 116.

The transceiver 120 may be configured to modulate the signals that areto be transmitted by the transmit/receive element 122 and to demodulatethe signals that are received by the transmit/receive element 122. Asnoted above, the WTRU 102 may have multi-mode capabilities. Thus, thetransceiver 120 may include multiple transceivers for enabling the WTRU102 to communicate via multiple RATs, such as UTRA and IEEE 802.11, forexample.

The processor 118 of the WTRU 102 may be coupled to, and may receiveuser input data from, the speaker/microphone 124, the keypad 126, and/orthe display/touchpad 128 (e.g., a liquid crystal display (LCD) displayunit or organic light-emitting diode (OLED) display unit). The processor118 may also output user data to the speaker/microphone 124, the keypad126, and/or the display/touchpad 128. In addition, the processor 118 mayaccess information from, and store data in, any type of suitable memory,such as the non-removable memory 106 and/or the removable memory 132.The non-removable memory 106 may include random-access memory (RAM),read-only memory (ROM), a hard disk, or any other type of memory storagedevice. The removable memory 132 may include a subscriber identitymodule (SIM) card, a memory stick, a secure digital (SD) memory card,and the like. In other embodiments, the processor 118 may accessinformation from, and store data in, memory that is not physicallylocated on the WTRU 102, such as on a server or a home computer (notshown).

The processor 118 may receive power from the power source 134, and maybe configured to distribute and/or control the power to the othercomponents in the WTRU 102. The power source 134 may be any suitabledevice for powering the WTRU 102. For example, the power source 134 mayinclude one or more dry cell batteries (e.g., nickel-cadmium (NiCd),nickel-zinc (NiZn), nickel metal hydride (NiMH), lithium-ion (Li-ion),etc.), solar cells, fuel cells, and the like.

The processor 118 may also be coupled to the GPS chipset 136, which maybe configured to provide location information (e.g., longitude andlatitude) regarding the current location of the WTRU 102. In additionto, or in lieu of, the information from the GPS chipset 136, the WTRU102 may receive location information over the air interface 116 from abase station (e.g., base stations 114 a, 114 b) and/or determine itslocation based on the timing of the signals being received from two ormore nearby base stations. It will be appreciated that the WTRU 102 mayacquire location information by way of any suitablelocation-determination method while remaining consistent with anembodiment.

The processor 118 may further be coupled to other peripherals 138, whichmay include one or more software and/or hardware modules that provideadditional features, functionality and/or wired or wirelessconnectivity. For example, the peripherals 138 may include anaccelerometer, an e-compass, a satellite transceiver, a digital camera(for photographs or video), a universal serial bus (USB) port, avibration device, a television transceiver, a hands free headset, aBluetooth® module, a frequency modulated (FM) radio unit, a digitalmusic player, a media player, a video game player module, an Internetbrowser, and the like.

FIG. 1C is a system diagram of the RAN 104 and the core network 106according to an embodiment. As noted above, the RAN 104 may employ aUTRA radio technology to communicate with the WTRUs 102 a, 102 b, 102 cover the air interface 116. The RAN 104 may also be in communicationwith the core network 106. As shown in FIG. 1C, the RAN 104 may includeNode-Bs 140 a, 140 b, 140 c, which may each include one or moretransceivers for communicating with the WTRUs 102 a, 102 b, 102 c overthe air interface 116. The Node-Bs 140 a, 140 b, 140 c may each beassociated with a particular cell (not shown) within the RAN 104. TheRAN 104 may also include RNCs 142 a, 142 b. It will be appreciated thatthe RAN 104 may include any number of Node-Bs and RNCs while remainingconsistent with an embodiment.

As shown in FIG. 1C, the Node-Bs 140 a, 140 b may be in communicationwith the RNC 142 a. Additionally, the Node-B 140 c may be incommunication with the RNC142 b. The Node-Bs 140 a, 140 b, 140 c maycommunicate with the respective RNCs 142 a, 142 b via an Iub interface.The RNCs 142 a, 142 b may be in communication with one another via anIur interface. Each of the RNCs 142 a, 142 b may be configured tocontrol the respective Node-Bs 140 a, 140 b, 140 c to which it isconnected. In addition, each of the RNCs 142 a, 142 b may be configuredto carry out or support other functionality, such as outer loop powercontrol, load control, admission control, packet scheduling, handovercontrol, macrodiversity, security functions, data encryption, and thelike.

The core network 106 shown in FIG. 1C may include a media gateway (MGW)144, a mobile switching center (MSC) 146, a serving GPRS support node(SGSN) 148, and/or a gateway GPRS support node (GGSN) 150. While each ofthe foregoing elements are depicted as part of the core network 106, itwill be appreciated that any one of these elements may be owned and/oroperated by an entity other than the core network operator.

The RNC 142 a in the RAN 104 may be connected to the MSC 146 in the corenetwork 106 via an IuCS interface. The MSC 146 may be connected to theMGW 144. The MSC 146 and the MGW 144 may provide the WTRUs 102 a, 102 b,102 c with access to circuit-switched networks, such as the PSTN 108, tofacilitate communications between the WTRUs 102 a, 102 b, 102 c andtraditional land-line communications devices.

The RNC 142 a in the RAN 104 may also be connected to the SGSN 148 inthe core network 106 via an IuPS interface. The SGSN 148 may beconnected to the GGSN 150. The SGSN 148 and the GGSN 150 may provide theWTRUs 102 a, 102 b, 102 c with access to packet-switched networks, suchas the Internet 110, to facilitate communications between and the WTRUs102 a, 102 b, 102 c and IP-enabled devices.

As noted above, the core network 106 may also be connected to thenetworks 112, which may include other wired or wireless networks thatare owned and/or operated by other service providers.

FIG. 1D shows an example communication case where MTC devices 180communicate with an MTC server 160. An MTC device 180 is a WTRU equippedfor machine type communication, which may communicate through a publicland mobile network (PLMN) with an MTC server(s) 160 and/or other MTCdevice(s) 180. An MTC server 160 is a server, which communicates to thePLMN itself, and to MTC devices 180 through the PLMN. The MTC server 160may have an interface which may be accessed by the MTC user 170. The MTCuser 170 uses the service provided by the MTC server 160. In thisexample, the MTC server 160 is located in the operator domain 165, butmay be located outside the operator domain 165. The MTC devices 160 maycommunicate with one or more MTC servers 160, and may also communicateeach other. The network operator provides network connectivity to theMTC server(s).

It should be noted that the embodiments disclosed herein may beimplemented in any type of wireless communication systems including, butnot limited to, UMTS, long term evolution (LTE), cdma2000, IEEE 802.16,GERAN, and the like. It should be noted that the embodiments disclosedherein are applicable to both mobile-originated-only feature and theinfrequent mobile terminated feature, and the terminology“mobile-originated-only mode” covers “infrequent-mobile-terminated mode”as well.

In accordance with one embodiment, a WTRU may switch back and forthbetween a mobile-originated-only mode 210 and amobile-originated-and-terminated mode 220 based on a predeterminedtrigger(s). FIG. 2 shows a transition between the mobile-originated-onlymode 210 and the mobile-originated-and-terminated mode 220.Alternatively, the WTRU may configure itself, or may be pre-configured,to operate in the mobile-originated-only mode 210. The operation in themobile-originated-only mode may be triggered by an explicit or implicittrigger, (e.g., a command from the network, a preconfigured schedule, orthe like). The WTRU may be configured to operate only in themobile-originated-only mode. In this case, a trigger may not benecessary to initiate or resume the operation in themobile-originated-only mode.

In the mobile-originated-and-terminated mode 220, the WTRU may listen toa paging channel or a paging indicator channel, or the like, (hereaftercollectively “paging channel”), and/or perform mobility managementprocedures. In the mobile-originated-and-terminated mode 220, thenetwork may reach the WTRU, for example, to perform tests, softwareupdates, to establish a call, etc.

In the mobile-originated-only mode 210, the WTRU may perform no, or asubset of, idle mode procedures that may be performed in themobile-originated-and-terminated mode. The WTRU may not perform certainmobility management procedures as it does not need to update itslocation to the network, or may not listen to a paging channel, since itis assumed that the WTRU will not receive calls. The functionalitiesthat may be performed in the mobile-originated-only mode are explainedin detail below.

The WTRU may be initially in a mobile-originated-only mode 210, and maytransition to the mobile-originated-and-terminated mode 220, forexample, once the WTRU initiates communication with the network. Thenetwork may take the WTRU out of the mobile-originated-only mode 210.The WTRU may exit the mobile originated-only mode 210 based on a timeror events, or the like.

In the mobile-originated-only mode 210, the WTRU may remain attached tothe network, (e.g., registered with, and authenticated to, the network).Since the WTRU remains attached, a transition to a connected state wouldbe much faster than the case the WTRU is detached.

The WTRU may not be reachable by the network while in themobile-originated-only mode 210. Alternatively, the WTRU in themobile-originated-only mode 210 may support a mechanism(s) to be reachedby the network on some occasions.

The power savings in the mobile-originated-only mode would be very largeas the device does not need to perform predetermined or configuredbackground activities, such as paging monitoring, intra-cell,inter-cell, or inter-radio access technology (RAT) measurements incontrast to the normal idle mode.

Functionalities supported in the mobile-originated-only mode areexplained hereafter.

In the mobile-originated-only mode, a WTRU may not perform pagingmonitoring. Consequently, the WTRU may not be able to receive mobileterminated calls and notification of the system information change viathe paging channel.

In the mobile-originated-only mode, the WTRU may not perform cellreselection. The WTRU may not perform neighbor cell measurements for thecell reselection. Alternatively, the WTRU may perform neighbor cellmeasurements to determine whether a new cell needs to be selected, butmay not perform other procedures, such as location area update, routingarea update, or tracking area update, (hereafter collectively “locationarea update”). If the WTRU reselects a new cell according to theneighbor cell measurements, the WTRU may acquire and store the systeminformation of the new cell, or alternatively may wait for a trigger,(e.g., moving out of the mobile-originated-only mode, a trigger for anRRC connection, or the like), before acquiring the system information.

In the mobile-originated-only mode, the WTRU may not perform a locationarea update even if a cell in a new location area, routing area, ortracking area, (hereafter collectively “location area”), is selected, ora new public land mobile network (PLMN) is entered. Alternatively,entering a new PLMN may be a trigger to perform a location area update.

Alternatively, while in the mobile-originated-only mode, the WTRU mayperform a subset of the functionalities that are performed in an idlemode. For example, a WTRU in the mobile-originated-only mode may notperform background check for higher priority PLMN search, cellreselection, or paging monitoring, etc.

The WTRU may operate in the mobile-originated-only mode on a per PLMNbasis. For example, the WTRU may have a list of allowed PLMNs thatindicate the mode of operation for each PLMN, (i.e., amobile-originated-only mode or a mobile-originated-and-terminated modefor each allowed PLMN). The list may be maintained in the WTRU, forexample, in the universal subscriber identity module (USIM).

WTRUs, (i.e., MTC devices), may be mobile, may have limited mobility, ormay be stationary. In case WTRUs may move anywhere, no cell reselectionimplies no paging monitoring and no location area updates. No locationarea updates imply no paging because the network does not know where theWTRU is located. In contrast, stationary WTRUs may not perform mobilityprocedures such as cell reselection, location area updates, or the like.In this case, even though the WTRUs do not perform location areaupdates, the network can still find the WTRUs since there is no changein location, therefore the WTRUs can still monitor the paging channel.In this case the WTRUs may have a longer discontinuous reception (DRX)cycle length in order to allow for battery savings. If the WTRU has alimited mobility, (e.g., the WTRU remains in the same location area oris restricted to a group of cells), the WTRU may not perform locationupdates, but the WTRU can be paged since the location is known.

The mobile-originated-only mode may support one or a combination of theabove functionalities for the mobile, limited mobility, or stationaryWTRUs. Table 1 shows example options of supported functionalities forthe mobile, stationary, and limited mobility WTRUs in themobile-originated-only mode. It should be noted that the functionalitieslisted in Table 1 are not exhaustive and other functionalities may beadded.

TABLE 1 Option 4 Option 5 Func- Option 1 Option 2 Option 3 (No (Limitedtionalities (Mobility) (Mobility) (Mobility) Mobility) Mobility) PagingNo No No Yes Yes monitoring Cell Yes Yes No No Yes reselection LocationYes No No No No update

In option 1, a WTRU may not perform paging monitoring but may performcell reselection and location update. The WTRU may read a broadcastchannel once the WTRU selects or reselects a cell or when the WTRU movesout of the mobile-originated-only mode, but may not be notified ofchanges in the broadcast channel information since the WTRU does notmonitor the paging channel. When the WTRU needs to transmit, the WTRUmay exit the mobile-originated-only mode, and check if there are anychanges in the system information. For value tag system informationblocks (SIBs), the WTRU may verify if there are changes in the valuetags. For periodic SIBs, the WTRU may read the SIBs if the validity hasexpired. If there are any changes, the WTRU obtains the systeminformation, and then starts a transmission.

The WTRU may inform the network that the WTRU exited themobile-originated-only mode. The network may then update the stateinformation that it may have stored for the WTRU, and may not wait forthe WTRU to establish a connection with the network before sending adownlink transmission (signaling or data) to the WTRU. The indicationmay be sent to the network in the radio resource control (RRC) ornon-access stratum (NAS) messages. If the indication is sent over RRCmessages, (e.g., RRCConnectionSetupComplete), the RAN node, (e.g., RNC,eNode B), may forward this indication to the mobility management entity(MME)/serving GPRS support node (SGSN) over the S1/radio access networkapplication part (RANAP) messages. Alternatively, the WTRU may send anNAS message, such as a tracking area update (TAU) message with thisindication while setting the ‘active flag’ bit in the TAU message to ‘1’that indicates to the network to establish the user plane bearers afterthe TAU procedure is completed. This may be done instead of sending aservice request message which is 4-octets long and does not have a spaceto include such indication. Alternatively, an extended service requestor a modified service request message may be sent with an additionalinformation element (IE) to provide this indication to the core network,(e.g., MME or SGSN).

In option 2, a WTRU may not perform paging monitoring and location areaupdate but may perform neighbor cell measurements and cell re-selection.Because the WTRU is performing cell reselection the WTRU may read thebroadcast channel every time a cell is re-selected. However, the WTRUmay not be notified of the broadcast information changes, because theWTRU does not monitor the paging channel. Alternatively, the WTRU mayperform cell reselection, but may not acquire and store the systeminformation. The WTRU may wait to transition out of themobile-originated-only mode, or until an uplink transmission isinitiated before acquiring and storing the system information.

When the WTRU needs to transmit, the WTRU may exit themobile-originated-only mode, and check if there are any changes in thesystem information. For value tag SIBs, the WTRU may verify if there arechanges in the value tags. For periodic SIBs, the WTRU may read the SIBsif the validity has expired. If the WTRU did not acquire some of theSIBs it may read and acquire the remaining SIBs. If there are changes inthe location area (i.e., location area, routing area, or tracking area),the WTRU may perform a location update procedure. If the network detectsa location area update, the network is aware that the WTRU has data totransmit and may allocate resources for the WTRU to transmit the data.Alternatively, the WTRU may explicitly indicate with the location areaupdate that it wants to performs uplink transmissions.

In option 3, a WTRU may not perform paging monitoring, cell reselection,or location update. When the WTRU needs to transmit, the WTRU may exitthe mobile-originated-only mode, and verify if the current cell is stilla suitable cell. If it is, the WTRU may remain in the same cell. If itis not, the WTRU may perform a cell reselection procedure by performingmeasurements on the neighbor cells. If the neighbor cells are notsuitable, the WTRU may perform initial cell selection. The WTRU may readthe broadcast channel in the selected cell. If the selected cell is thesame as the previous cell, the WTRU may only check if there are anychanges in the system information. For value tag SIBs, the WTRU mayverify if there are changes in the value tags. For periodic SIBs, theWTRU may read the SIBs if the validity has expired. If there are changesin the location, (location area, routing area, or tracking area), theWTRU may perform location update procedure. The WTRU may then starttransmission.

In option 4, a WTRU may perform paging monitoring but may not performcell reselection and location update. Option 4 is for the stationaryWTRU. Since the WTRU is stationary, there is no need to perform cellreselection or location update. When the WTRU needs to transmit, theWTRU may exit the mobile-originated-only mode, and may starttransmission.

In option 5, a WTRU may perform paging monitoring and cell reselectionbut may not perform location update. Option 5 is for a WTRU with limitedmobility, (e.g., the WTRU remains in the same location area or it isrestricted to a group of cells, which could be a single cell). Since theWTRU remains in the same location area, there is no need to performlocation updates, and the WTRU can be paged without location updatessince the location is known. When the WTRU needs to transmit, the WTRUmay exit the mobile-originated-only mode, and may start transmission.

The WTRU may signal to the network that it supports themobile-originated-only mode. This notification may imply a set offunctionalities that are supported by the WTRU in themobile-originated-only mode. Alternatively, the WTRU may specificallynotify the network the functionalities supported by the WTRU in themobile-originated-only mode, (e.g., paging monitoring, cell reselection,and/or location update).

In order to control the behaviors of the WTRU in themobile-originated-only mode, a new mobile-originated-only state or a newprofile configuration (hereafter referred to as “mobile-originated-onlystate or configuration”) may be defined. The new mobile-originated-onlystate or configuration may be defined in the radio resource control(RRC) and/or non-access stratum (NAS) layers. It should be noted thatthe mobile-originated-only state or configuration may be implementedwithout an additional RRC and/or NAS state or configuration, and theembodiments disclosed herein may be implemented with or without the newRRC and/or NAS states or configuration.

In accordance with one embodiment, the functionalities for the mobileoriginated-only-mode may be supported by a new RRC state. FIG. 3 is anexample universal terrestrial radio access (UTRA) RRC state diagram inaccordance with one embodiment. FIG. 4 is an example evolved universalterrestrial radio access (E-UTRA) RRC state diagram in accordance withanother embodiment. In FIGS. 3 and 4, in addition to the conventionalUTRA/E-UTRA RRC_CONNECTED and UTRA/E-UTRA RRC_IDLE states, theUTRA/E-UTRA RRC_IDLE_MO_ONLY state is defined to control the behavior ofthe WTRU and the network in the mobile-originated-only mode. The RRCstate transitions between RRC_CONNECTED and RRC_IDLE or RRC_ILDE_MO_ONLYare triggered by the RRC connection establishment or release. The RRCstate transitions between RRC_IDLE and RRC_IDLE_MO_ONLY may be triggeredby the explicit or implicit triggers, which will be explained in detailbelow.

In accordance with another embodiment, the functionalities in themobile-originated-only mode may be supported by an RRC IDLE state with anew RRC profile configuration that captures all the specific operationsin the mobile-originated-only mode. While operating in themobile-originated-only mode, the WTRU may use the new RRC configurationin the IDLE mode. The WTRU may store in its memory the new profileconfiguration, and this would allow the WTRU to rapidly switch from onemode to another without acquiring the new RRC configuration from thenetwork. The mobile-originated-only profile configuration may be sent tothe WTRU using a dedicated RRC signaling message encapsulated in theconventional RRC messages, such as a RRC connection release message, orany other messages. Alternatively, the network may send themobile-originated-only profile configuration over the SIBs. The WTRUoperating for the first time in the mobile-originated-only mode mayacquire the corresponding SIBs. When the WTRU switches out of this mode,the WTRU may store in a memory the mobile-originated-only configurationprofile, allowing the WTRU to switch back in this mode without aninterruption and without a need to reacquire the RRC configurationsassociated with this profile.

In accordance with another embodiment, a new state of the RRC idle modemay be defined. In this case, the RRC entity in the network side may ormay not be aware of the fact that the WTRU is in this state since, fromthe network point of view, the WTRU may simply be in an RRC idle mode.The NAS state on the network side may be different for the WTRU (e.g.,even if no new RRC state is used).

For the NAS support, the functionalities may be supported in a new NASstate. The WTRU may enter the new NAS state due to a trigger from thenetwork in an NAS message. The NAS message may be an accept messagewhich is sent from the network to the WTRU, (e.g., Attach Accept,Location Update Accept, and Tracking Area Update Accept, etc.).Alternatively, the transition to the new NAS state may be triggered bythe WTRU, (e.g., via an internal inactivity timer). In this case, theWTRU may notify the network that the WTRU enters the new NAS state.Specific periods of time, (e.g., specific time of a day), may bereserved for the WTRU to operate in this new NAS state. The transitionout of this new NAS state may be coordinated with the network based, forexample, on the time of the day. The WTRU may send a notification to thenetwork when the WTRU exits the new NAS state and becomes reachable. Thetriggers applicable to the RRC state transitions may be applied for theNAS state transitions, since the WTRU RRC and NAS may be synchronized,(i.e., using the same mode of operation (same state or configuration) atany given time).

An equivalent new mobile-originated-only NAS state may be configured onthe network side, (e.g., in the MME, SGSN, or the like). The eventsapplied for the WTRU may be applied to transition in and out of the NASstate at the network, (e.g., MME or SGSN). Based on network policy andevents, the new NAS state at the network may change for a specific WTRU.This may trigger the network, (e.g., MME or SGSN), to request the WTRUto exit or enter other states. Such indication may be provided over NASmessages or over RRC or OMA MD/OTA messages. An RAN-based indication mayalso be forwarded over S1AP or RANAP or other equivalent messages.

Alternatively, the functionalities may be supported by an NASidle/standby state with a new NAS profile/configuration. A newconfiguration may be provided to be supported in NAS evolved packetsystem (EPS) connection management (ECM) idle state (LTE), NAS packetmobility management (PMM) idle state (Iu mode), or NAS standby state(A/Gb mode). The modifications on this state may depend on thefunctionality supported, as described above.

Because the SGSN/MME may perform an implicit general packet radioservice (GPRS) detach any time after the WTRU reachable timer expires,the network may increase the value of this timer or disable it duringthis configuration mode of operation. The timer may be either the mobilereachable timer and/or the implicit detach timer.

Triggers for transitioning between the mobile-originated-only mode andthe mobile-originated-and-terminated mode, (i.e., transitions betweenthe RRC/NAS states or configuration), or for initiating and stoppingoperation in the mobile-originated-only mode are explained hereafter.The triggers may be explicit or implicit. The triggers disclosed belowmay be used in any embodiments disclosed above.

Transitions between the mobile-originated-only mode and themobile-originated-and-terminated mode, (i.e., transitions between theRRC/NAS states or configuration), may be signaled explicitly via an RRCmessage, (e.g., RRC connection release message). A new parameter,information element (IE), or field may be included in the RRC message totrigger the transition from the RRC connected state to themobile-originated-only state or configuration. Alternatively, theabsence of a specific field in the RRC message may signify to the WTRUthat the WTRU should operate in the mobile-originated-and-terminatedmode, (i.e., a conventional RRC/NAS states).

The network may signal the WTRU to transition between themobile-originated-only mode and the mobile-originated-and-terminatedmode, (i.e., transitions between the RRC/NAS states or configuration),by sending idle mode signaling, such as a paging message, a broadcastmessage, or a cell broadcast service (CBS) message, or the like.Transition from the mobile-originated-only mode and themobile-originated-and-terminated mode, (i.e., from the normal idle stateto the mobile-originated-only state or configuration, (i.e., transitionsbetween the RRC/NAS states or configuration)), may be triggered by apaging message, any NAS message, or the like.

The decision to trigger the transition of the state/configuration ofoperation may be based on network/operator policies, (e.g., the loadconditions of the network). The radio access network, (e.g., evolvedNodeB (eNB) or NodeB), may indicate this to the WTRU based onindications that are received over the SlAP or radio access networkapplication part (RANAP) messages in case of LTE or 3G system,respectively. For example, the mobility management entity (MME) may senda request to the eNB to change the mode of operation of the WTRU tomobile-originated-only mode and this may be done by introducing a new IEon the SlAP message, (e.g., UEContextModificaitonRequest, or the like).This also applies to equivalent messages on 3G system or GPRS EDGE radioaccess network (GERAN) equivalent messages between the radio accessnetwork (RAN) and the core network.

Alternatively, upon registration, (e.g., attach procedure), or locationarea update procedures, (e.g., location area update, routing areaupdate, or tracking area update, or combination of these), a WTRU mayindicate to the network its previous mode or setting of the operation,(e.g., respective RRC and NAS states or profile configurations). Thenetwork, (e.g., MME), may also indicate the mode of operation to be usedby the WTRU in the response message or any other NAS message, (e.g., EMMinformation or equivalent message). The WTRU may use the mode indicatedby the network with settings to operate in certain mode.

Alternatively, the WTRU may follow the network's suggested mode ofoperation, (e.g., mobile-originated-only mode). When the NAS entity inthe WTRU decides on the mode of operation, for example based on theindication from the MME, the NAS entity may inform the access stratum(AS)/RRC about the selected mode of operation.

Alternatively, the NAS or RRC entity in the WTRU may receive anindication about the configuration or mode of operation to use. Theindication may be received from a user via an interface, (e.g., aninterface on a vending machine), or the change of the settings due touser medication. Alternatively, the indication may be received via ashort message service (SMS) message and/or the open mobile alliance(OMA) device management (DM) or over-the-air (OTA) protocol.

The configuration or mode of operation may be changed due to a change ofdevice operation mode. For example, if the WTRU is operating in amobile-originated-only mode, a change of the device operation mode fromautomatic to manual, (e.g., request for manual closed subscriber group(CSG) selection or manual PLMN selection), may trigger the WTRU to exitthe mobile-originated-only mode, and a change from manual to automaticmode may trigger the WTRU to operate in a mobile-originated-only mode.

The transitioning between the mobile-originated-and-terminated mode andthe mobile-originated-only mode may be triggered implicitly when acertain condition(s) is met. For example, the condition may be based onan inactivity timer, (e.g., if no downlink data is received within apreconfigured time). Once the inactivity timer expires or reaches acertain value, the WTRU may transition from the mobile-originated-onlymode and the mobile-originated-and-terminated mode, (i.e., transitionsbetween the RRC/NAS states or configuration (i.e., from the normal idlestate to the mobile-originated-only state or configuration)), or viceversa.

The inactivity timer may be re-started or re-initialized based on anactivity, such as a transition to the normal RRC idle state from the RRCconnected state. Alternatively, the network may send a page message oridle mode signaling, (e.g., a CBS message), to re-start or re-initializethe inactivity timer and maintain the WTRU in themobile-originated-and-terminated mode. Alternatively, the inactivitytimer may be re-started or re-initialized while the WTRU is in an RRCconnected state.

When the inactivity timer expires, the WTRU may autonomously transitionto the mobile-originated-only sate/configuration, (with respective RRCand NAS states or profile configurations), without notifying the networkof the transition. Alternatively, the WTRU may autonomously transitionto the mobile-originated-only state or configuration and send anotification to the network about the transition. Alternatively, theWTRU may signal this trigger to the network and wait for an explicittrigger from the network to transition to the mobile-originated-onlystate or configuration.

Alternatively, the WTRU may transition from the mobile-originated-onlymode to the mobile-originated-and-terminated mode, in a periodicfashion, (e.g., once a day). Once the WTRU leaves themobile-originated-only mode, the WTRU may perform all, or a subset of,normal idle mode procedures, (e.g., listen to the paging channel,perform cell reselection or location update, etc.). The WTRU may send a“polling” message to the network to indicate that the WTRU exits themobile-originated-only mode and is now reachable. More specifically,when a periodic timer expires or when a certain time as configured bythe network or application is reached, the WTRU may transition to anormal idle mode, and may initiate a transmission to notify the networkthat the WTRU is operating in a mobile-originated-and-terminated mode.The message transmitted may be an RRC message, wherein a newestablishment cause or a new IE may be included to indicate thistrigger. Alternatively, the message may be an NAS message. The NASmessage may contain the location area, a new cause, and/or an additionalinformation element(s) indicating that the WTRU has exited themobile-originated-only mode. The network may then know that the WTRU isreachable and page the WTRU if it needs to reach the WTRU.

Alternatively, the network may broadcast a new flag in a particular SIBand the WTRU may receive the broadcast channel to monitor the SIBaccording to a configured periodicity. The monitoring time maycorrespond to a periodic timer or to an absolute time and lengthconfigured by the network. During that time the WTRU may remain in themobile-originated-only mode and just monitor the SIB, rather thantransitioning to the RRC idle mode. If the flag in the SIB is set, theWTRU may move out of the mobile-originated-only mode, may read all SIBsand start monitoring the paging channel, etc. Alternatively, if the flagis set the WTRU may trigger a “polling message” to indicate to thenetwork that the WTRU has moved out of the mobile-originated-only modeand may now be paged for a pre-defined or configured period of time.When the WTRU leaves the mobile-originated-only mode and reads the SIB,the flag in the SIB may indicate the WTRU to either monitor the pagingchannel, or to send a “polling” message to notify that the WTRU becamereachable, or to return to the mobile-originated-only mode. When thelength of the period expires and the WTRU has not received any paging orno flag was set in the SIB, the WTRU may transition back to themobile-originated-only mode.

An MTC subscriber may trigger a specific MTC device or an MTC group totransition from the mobile-originated-only mode to themobile-originated-and-terminated mode, or vice versa. An MTC subscriberis a legal entity having a contractual relationship with the networkoperator to provide a service to one or more MTC devices. An MTC groupis a group of MTC devices that belong to the same MTC subscriber. Inaccordance with one embodiment, an address field of a message may allowthe MTC subscriber to send a unicast, multicast and broadcast trigger toa specific MTC device or an MTC group. The address field may bepartitioned to reserve a range of addresses for unicast and multicastaddresses, (e.g., the most significant bit (MSB) of the address fieldmay be used to indicate a multicast or unicast address). A specificaddress may be reserved to indicate a broadcast address, (e.g., the “allones” address).

A WTRU may transition between the mobile-originated-and-terminated modeand the mobile-originated-only mode periodically. When the WTRU is inthe mobile-originated-only mode, it may be referred to be in theunreachable period, and when the WTRU is out of themobile-originated-only mode, it may be referred to be in a reachableperiod. FIG. 5 shows an example reachable period and unreachable period.The WTRU may alternate between the unreachable period and the reachableperiod based on a configured rule(s).

The WTRU may enter and exit the unreachable period based on any implicitor explicit triggers disclosed above. The WTRU may exit the unreachableperiod based on the reachability cycle or based on an event such asexpiration of a timer or uplink activity. Once the WTRU exits theunreachable period, the WTRU may remain in the reachable period, (i.e.,in “regular” idle mode), until a new unreachability cycle starts.Alternatively, the network may instruct the WTRU to return to theunreachable period. This instruction may be sent via a broadcastmessage, a paging message, or the like. Alternatively, the network mayinstruct the WTRU to establish an RRC connection and enter an RRCconnected mode.

Explicit trigger may be a message from the network to the WTRU. Thismessage may be an NAS message, an RRC dedicated message, a broadcastmessage, a paging message, or the like. In case the trigger is from theRNC/eNodeB, the trigger information may also be propagated to the corenetwork, so that the SGSN/MME are aware of the WTRU reachability status.

Implicit triggers may be an event, such as the expiration of an activitytimer or a pre-configured reachability cycle. In case of implicittrigger, the WTRU may notify the network that it is entering theunreachable period or the reachable period. The WTRU may notify the NASor RRC entities, or both. In case, the WTRU notifies the RRC entity, theinformation may be propagated to the core network, so that the SGSN/MMEare aware of the WTRU reachability status. The reachability cycle of theWTRU may be pre-configured in the network, in which case a notificationfrom the WTRU may not be needed.

For the operations in the mobile-originated-only mode (including theinfrequent-mobile-terminated mode), the WTRU may receive from thenetwork, or be pre-configured with, a configuration including theunreachability cycle. The configuration may indicate timing foractivating the first cycle of the unreachable period and/or the durationof the cycle. The WTRU may receive the configuration from the corenetwork via a message, (e.g., Attach Accept, Location Update Accept, andTracking Area Update Accept), or from the radio access network (RAN),(e.g., via an RRC message). If the configuration is received from theRAN, the RAN may propagate it to the core network nodes. If the WTRU hasbeen pre-configured with the unreachability cycle, the WTRU may informthe parameters to be used to the network entity in the RAN, (e.g., RNCor eNodeB), and/or in the core network, (e.g., SGSN, MME). Thisnotification may be part of the NAS message, (e.g., Attach, LocationUpdate, and Tracking Area Update) or the RRC message, (e.g., RRCconnection request). If the notification is sent as an RRC message, itmay be propagated to the core network nodes. The reachable period may beconfigured in terms of an absolute time and period. More specifically,the network may specify an absolute time, (e.g., 2 pm), and a period,(e.g., X hours, minutes, or seconds). More than one absolute time may bespecified within a day or certain time period. The WTRU configures itsRRC and NAS entities in terms of the unreachability cycle to be used andthe RRC entity may then configure the lower layers to perform thefunctions as disclosed above.

At the start of the unreachability cycle, the WTRU may go to sleep andwake up at the end of the unreachability cycle unless the applicationlayer or other events trigger the WTRU to wake up in the middle of theunreachable period. The unreachable and reachable periods may define theperiods in which the WTRU transitions between the mobile-originated-onlymode and the mobile-originated-and-terminated mode.

The WTRU may wake up (or exit the mobile-originated-only mode) upon arequest to place a call, (e.g., emergency call in a packet-switched (PS)or circuit-switched (CS) domain, or other distress signal that may beintroduced for low priority devices). The WTRU may not enter themobile-originated-only mode until the call, (e.g., the emergency call),is finished or until there are no more resources for the call (e.g.,until a packet data network (PDN) or packet data protocol (PDP) contextthat was used for the emergency call is cleared or deactivated). TheWTRU may not enter the mobile-originated-only mode if the WTRU isattached for emergency services.

At the end of the unreachable period, the WTRU wakes up and acquiresnetwork synchronization and basic cell information using the previouslystored network information, such as carrier frequency, cell ID, PLMN ID,and so on. If the WTRU is still within a range of the previous servingcell, the WTRU may verify that SIB has not changed. If the SIB has notchanged, the WTRU may use the previously stored SIB information. If theSIB has changed, the WTRU may re-acquire the SIB information. The WTRUmay calculate the next start of the unreachability cycle and enter theidle mode operation for the duration of the reachable period. The WTRUmay resume paging monitoring, cell reselection, and other idle modeprocedures. If the location area has changed, the WTRU may trigger alocation area update.

If the previous serving cell is no longer within a range, the WTRU mayundertake a full cell search while keeping the PLMN. The WTRU mayperform cell reselection and location area update.

At the end of the reachable period, the WTRU may end the idle modeprocedures and enter the unreachable period and go to sleep.

If the WTRU transitions out of the mobile-originated-only mode to make atransmission, the WTRU may remain as reachable for a certain period oftime. The time period may be determined with respect to the initiationof the first transmission, (e.g., RRC connection establishment), withinthe transmission of an NAS message, within a data transmission, or thelike. The time period may be re-initiated after every transmissions orreception. Once the time period expires the WTRU may autonomouslyrelease an RRC connection (if applicable) and move to themobile-originated-only mode. Alternatively, the WTRU may release the RRCconnection, move to a mobile-originated-and-terminated mode (i.e.,normal idle mode in this case), and monitor an additional inactivitytimer, after expiration of which the WTRU transitions to themobile-originated-only mode.

The network may broadcast an indication that WTRUs in themobile-originated-only mode come out of the mobile-originated-only mode.A NodeB(s) may send a special information element to request WTRUs tocome out of the mobile-originated-only mode, for example, in the systeminformation, (e.g., SIB1). This may be broadcast by all NodeBs, or by atargeted NodeB(s). For example, the special information element may besent by a NodeB(s) where the information about the number ofmobile-originated-only mode WTRUs is needed. The special informationelement may include a flag to indicate whether themobile-originated-only mode WTRUs are required to come out of themobile-originated-only mode, a list of target WTRUs (this may be used ifthe network wants to reach a specific WTRU(s), for example, to track thelocation of the WTRU(s)), or a group identification for a group ofWTRUs, (the group identification may be related to WTRU access class orsome other WTRU specific feature). The special information element mayalso include information related to how and when the WTRUs come out ofthe mobile-originated-only mode. This may be necessary as the specialinformation element may trigger more than one WTRU to come out of themobile-originated-only mode, which allows the network to spread out (intime) the activation of these WTRUs and have some control over theresulting load the activated WTRUs would generate on the access network.

A WTRU in the mobile-originated-only mode may monitor, on a regularbasis, the system information to acquire the special informationelement. At these instances, the WTRU may initially try to acquire thesystem information from the last known cell on which it camped. If it isnot possible, (e.g., if the last camped cell is no longer in a range),the WTRU may perform a cell selection to acquire the system information.The WTRU may not camp on the new cell, but acquire the SIB containingthe special information element.

Upon reading the special information element, the WTRU may evaluate ifit needs to come out of the mobile-originated-only mode, for example,based on the type of information contained in the system information. Ifthe network has targeted specific WTRUs, (e.g., the special informationelement contains a list of specific WTRU addresses or a groupidentification), the WTRU may come out of the mobile-originated-onlymode if the WTRU is included in the target list. If not, the WTRU mayremain in the mobile-originated-only mode. If the WTRU is in the targetlist, the WTRU may determine the timing to transition out of themobile-originated-only mode. This may be immediate, or based on someparameters that are included in the special information element.

Once the WTRU receives an indication to trigger a mobile originatedcommunication, (i.e., to come out of the mobile-originated-only mode),the WTRU may perform a cell selection and initiate an RRC connectionrequest to the network. Upon receiving the RRC connection requestmessage, the network may determine if it needs to move the WTRU out ofthe mobile-originated-only mode and send an RRC connection setup or anRRC connection reject message to make the WTRU come out of themobile-originated-only mode. The WTRU may be required to send a pollingmessage to the network.

It should be noted that the embodiments described above may be usedindependently or in any combination.

Although features and elements are described above in particularcombinations, one of ordinary skill in the art will appreciate that eachfeature or element can be used alone or in any combination with theother features and elements. In addition, the methods described hereinmay be implemented in a computer program, software, or firmwareincorporated in a computer-readable medium for execution by a computeror processor. Examples of computer-readable media include electronicsignals (transmitted over wired or wireless connections) andcomputer-readable storage media. Examples of computer-readable storagemedia include, but are not limited to, a read only memory (ROM), arandom access memory (RAM), a register, cache memory, semiconductormemory devices, magnetic media such as internal hard disks and removabledisks, magneto-optical media, and optical media such as CD-ROM disks,and digital versatile disks (DVDs). A processor in association withsoftware may be used to implement a radio frequency transceiver for usein a WTRU, UE, terminal, base station, RNC, or any host computer.

1. (canceled)
 2. (canceled)
 3. (canceled)
 4. (canceled)
 5. (canceled) 6.(canceled)
 7. (canceled)
 8. (canceled)
 9. (canceled)
 10. (canceled) 11.(canceled)
 12. (canceled)
 13. (canceled)
 14. (canceled)
 15. A wirelesstransmit/receive unit (WTRU) supporting machine-type communications foruse in a wireless network, comprising: a first WTRU timer that indicatesto the WTRU to change from a mobile originated-and-terminated-mode to amobile-originated-only mode, in which the WTRU is attached to a wirelesscommunications network and performs no cell reselection, no locationupdate procedures, no system information monitoring, or no pagingmonitoring while attached to the network; a second WTRU timer thatindicates to the WTRU to change from the mobile-originated-only mode tothe mobile originated-and-terminated-mode; and a processor comprisingexecutable instructions to change the WTRU from the mobileoriginated-and-terminated-mode to the mobile-originated-only mode inresponse to the first WTRU timer, and to change the WTRU from themobile-originated-only mode to the mobile originated-and-terminated-modein response to a mobile origination event or the second WTRU timer. 16.The WTRU of claim 15, wherein the processor further comprises executableinstructions to set the first WTRU timer based on a time parameterreceived from the wireless network.
 17. The WTRU of claim 16, whereinthe time parameter comprises a cycle time and a reachable period. 18.The WTRU of claim 16, wherein the time parameter comprises a reachableperiod for operating in the mobile originated-and-terminated-mode. 19.The WTRU of claim 15, wherein the processor is further configured togenerate a message to send to the wireless network that indicates to thewireless network that the WTRU can operate in the mobile-originated-onlymode.
 20. The WTRU of claim 19, wherein the message is one of a trackingarea update message, a routing area update message, and an attachrequest message.
 21. The WTRU of claim 19, wherein the message is an RCCmessage.
 22. The WTRU of claim 15, wherein the WTRU comprises a batterythat provides power for the WTRU and the WTRU uses less battery power ona per unit time basis in the mobile-originated-only mode than when theWTRU is in the mobile originated-and-terminated-mode.
 23. A method ofusing a wireless transmit/receive unit (WTRU) supporting machine-typecommunications in a wireless network, comprising: changing the WTRU froma mobile originated-and-terminated-mode to a mobile-originated-onlymode, in which the WTRU is attached to a wireless communications networkand performs no cell reselection, no location update procedures, nosystem information monitoring, or no paging monitoring while attached tothe network, in response to a first WTRU timer; and changing the WTRUfrom the mobile-originated-only mode to the mobileoriginated-and-terminated-mode in response to a second WTRU timer. 24.The method of claim 23, further comprising setting the WTRU first timerbased on a time parameter received from the wireless network.
 25. Themethod of claim 23, further comprising setting the WTRU second timerbased on a time parameter received from the wireless network.
 26. Themethod of claim 24, wherein the time parameter comprises a cycle timeand a reachable period.
 27. The method of claim 24, wherein the timeparameter comprises a cycle time and an unreachable period.
 28. Themethod of claim 24, wherein the time parameter comprises a time.
 29. Themethod of claim 24, wherein the time parameter comprises a time.
 30. Themethod of claim 23, further comprising generating a message to send tothe wireless network that indicates to the wireless network that theWTRU can operate in the mobile-originated-only mode.
 31. The method ofclaim 30, wherein the message is one of a tracking area update message,a routing area update message, and an attach request message.
 32. Themethod of claim 30, wherein the message is an RCC message.
 33. Themethod of claim 23, wherein the WTRU comprises a battery that providespower for the WTRU and the WTRU uses less battery power on a per unittime basis in the mobile-originated-only mode than when the WTRU is inthe mobile originated-and-terminated-mode.